ci: enable branch-specific npm publishing#464
Merged
ParidelPooya merged 2 commits intomainfrom Mar 9, 2026
Merged
Conversation
ParidelPooya
force-pushed
the
ci/multi-branch-npm-publish
branch
from
011fc89 to
4865fec
Compare
Add ref parameter to checkout action in npm-publish workflow to use the target branch specified when creating GitHub releases. This enables publishing from different branches (main, v1.x) using the correct source code. Operator manages branch-version alignment during release creation.
ParidelPooya
force-pushed
the
ci/multi-branch-npm-publish
branch
from
4865fec to
778908c
Compare
bchampp
approved these changes
Mar 9, 2026
ayushiahjolia
approved these changes
Mar 9, 2026
yaythomas
approved these changes
Mar 9, 2026
ParidelPooya
added a commit
that referenced
this pull request
Mar 9, 2026
*Description of changes:* Add ref parameter to checkout action in npm-publish workflow to use the target branch specified when creating GitHub releases. This enables publishing v1.x.x from v1.x branch and v2.x.x from main branch using the correct source code for each version line. *Issue #, if available:* #461
ParidelPooya
added a commit
that referenced
this pull request
Mar 9, 2026
*Description of changes:* Add ref parameter to checkout action in npm-publish workflow to use the target branch specified when creating GitHub releases. This enables publishing v1.x.x from v1.x branch and v2.x.x from main branch using the correct source code for each version line. *Issue #, if available:* #461
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes:
Add ref parameter to checkout action in npm-publish workflow to use the target branch specified when creating GitHub releases. This enables publishing v1.x.x from v1.x branch and v2.x.x from main branch using the correct source code for each version line.
Issue #, if available:
#461